System And Apparatus For Providing Authenticable Electronic Communication

ABSTRACT

The present disclosure provides generally for systems and methods of authenticating one or more aspects of electronic communication. According to the present disclosure, authenticable communications may allow for authentication of at least a portion of the content of the electronic communication, which may limit potential damage caused by fraudulent communications. In some aspects, an authenticable communication may allow a recipient to confirm that the indicated source is the actual source of the authenticable communication. In some embodiments, the authentication may not require an exchange of encrypted communications or an exchange of communications solely within the same communication system. Authenticable communications may provide a separate layer of security that may allow a recipient to review the contents with confidence that the communication is not fraudulent. Further, authenticable communications may provide the additional security without requiring specialized software.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation in part of and claims priority to andthe full benefit of U.S. Nonprovisional patent application Ser. No.16/858,315 (filed Apr. 24, 2020, and titled “SYSTEM AND APPARATUS FORPROVIDING AUTHENTICABLE ELECTRONIC COMMUNICATION”), which claimedpriority to and the full benefit of U.S. Nonprovisional patentapplication Ser. No. 16/458,693 (filed Jul. 1, 2019, and titled “SYSTEMAND APPARATUS FOR PROVIDING AUTHENTICABLE ELECTRONIC COMMUNICATION”),which claimed priority to and the full benefit of U.S. ProvisionalPatent Application Ser. No. 62/809,669 (filed Feb. 24, 2019, and titled“SYSTEM AND APPARATUS FOR PROVIDING AUTHENTICABLE ELECTRONICCOMMUNICATION”), the entire contents of which are incorporated in thisapplication by reference.

BACKGROUND OF THE DISCLOSURE

Forgery has perplexed and stymied human trust since writing and the useof paper became pervasive, particularly for financial transactions. Oneof the first prohibitions against forgery was when the Romans outlawedfalsifying documents that transferred land to heirs. Over time theextent of forgery broadened to include tampering, counterfeiting, andmisrepresentation. Illegitimate conveyances evolved into falsifyingpaper notes as well. For example, in England during the early 19^(th)century, 1-pound notes were incredibly easy to replicate, which lead tothe mass incarceration of approximately 100,000 people over a 7-yearperiod. Laws continually developed to match the sophistication levels ofthose committing the forgery, though it was still difficult to identifyincredibly convincing forgeries.

With the promulgation of technology, these issues increased ahundredfold. Where technology is meant to improve the quality of lifeand streamline certain processes, the continued concern of forgery ormisrepresentation has denied more sensitive transactions the benefit oftechnology. Complex financial transactions or something as relativelystraightforward as a house closing still rely on traditional methods ofapproval and confirmation. Certain banks warn consumers not to trustemail communications sent from them or not to respond to phone callswhere someone claims to be a representative from the bank. As a result,despite all the innovation that has occurred, the old models remain,meaning people still need to appear in person or by proxy for anythinginvolving money transferring hands.

The problem continues even for less sensitive, but still incrediblycritical, communications. Employees are now warned that, because of thesophistication of external technologies and techniques like phishing,not to click on certain emails or not to click on links within an email,even when those emails are purportedly from someone within their owncompany. This is compounded when an employee regularly receivescommunication from someone like a financial officer who has timeconstraints on closing a matter that involves money and expects theemployee to diligently follow through on their requests. Sometimes thevolume is such that it does not make sense for the financial officer topersonally appear and make each request to the employee.

As a result, email authentication is used to prevent phishing, spoofing,spamming, and other forms of fraud. Because of the rising sophisticationof these techniques, false senders were able to get passwords, accountinformation, personally identifiable information, and financialinformation. False senders may also manipulate recipients to takecertain actions, which could be harmful to themselves or others. Emailauthentication may help an internet service provider (ISP) properlyidentify the sender of an email and intercept or prevent thesecommunications from going through. This practice is meant to simplifyand automate the process of identifying a sender and is also supposed toimprove the likelihood that a legitimate email goes to its intendedrecipient.

Three major forms of email authentication systems include the senderpolicy framework (SPF), the DomainKeys identified mail (DKIM) method,and the Domain-based Message Authentication, Reporting, and Conformance(DMARC) system. SPF cross-checks the domain in a sender's email againstthe published record the sender has registered in the Domain Name System(DNS). DKIM is a cryptographic, signature-based form of emailauthentication, where public/private key pairs are generated and checkedagainst each other to ensure that the message was not altered and wasfrom the original sender. DMARC mixes the SPF and DKIM systems, whichallows an administrator to specify which mechanism is used when sendingan email from their domain. DMARC does not directly address whether anemail is spam or fraudulent. Instead, it requires that a message passeseither DKIM or SPF validation as well as a process called alignment.

Despite these current solutions to email communication authentication,it is clear the solutions require extensive integration and technicalunderstanding that may confuse and unnecessarily complicate an everydayemail user. Organizations with complex systems may be able to educateemployees or customers to these methods, but there is still a steepeducation curve involved as well as an implementation process. Further,some of these authentication processes still cannot indicate whether anemail is fraudulent.

SUMMARY OF THE DISCLOSURE

What is needed is a streamlined system and method to authenticate one ormore aspects of an electronic communication on an individual ororganization-wide basis. This would allow one or more recipients toconfirm, for example and not limitation, whether the content of theelectronic communication has been adjusted, altered, or otherwisemodified in some way. In some embodiments, an authentication system maygenerate various options to authenticate a source of the authenticablecommunication.

The present disclosure relates to a computer-implemented method forproviding an authenticable communication, wherein thecomputer-implemented method may comprise: receiving an electroniccommunication comprising at least an actual source and original content;and converting the electronic communication to an authenticablecommunication. In some aspects, converting may comprise generating atleast one authentication mechanism for the authenticable communication,wherein the at least one authentication mechanism at least partiallycomprises at least one correlation between at least one detectableelement of the electronic communication and an initial transmission ofthe electronic communication or the actual source of the electroniccommunication, wherein the initial transmission of the electroniccommunication comprises a primary data transmission pathway; and storingthe at least one authentication mechanism in at least one memoryresource.

In some aspects, an authenticable communication may comprise an actualsource; at least one potential recipient, original content, and at leastone authentication mechanism, wherein the authentication mechanism mayallow one or more recipients to authenticate one or more aspects of theauthenticable communication. In some implementations, correspondingcomputer systems, apparatus, and computer programs recorded on one ormore computer storage devices, may be configured to perform the actionsof the methods. Implementations of the described techniques may comprisehardware, a method or process, or computer software on acomputer-accessible medium.

A system of one or more computers may be configured to performparticular operations or actions by virtue of having software, firmware,hardware, or a combination of them installed on the system that inoperation may cause the system to perform the actions. One or morecomputer programs may be configured to perform particular operations oractions by virtue of including instructions that, when executed by dataprocessing apparatus, may cause the apparatus to perform the actions. Insome aspects, corresponding computer systems, apparatus, and computerprograms recorded on one or more computer storage devices, may beconfigured to perform the actions of the methods.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, that are incorporated in and constitute apart of this

specification, illustrate several embodiments of the disclosure and,together with the description, serve to explain the principles of thedisclosure:

FIG. 1 illustrates an exemplary system of source authentication of anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 2A illustrates an exemplary authenticable communication with anicon authentication and barcode authentication, according to someembodiments of the present disclosure.

FIG. 2B illustrates an exemplary authenticable communication with a QRcode authentication and a numeric grid, according to some embodiments ofthe present disclosure.

FIG. 3 illustrates an exemplary graphical user interface (GUI) for anauthentication system, according to some embodiments of the presentdisclosure.

FIG. 4 illustrates exemplary authentication methods, according to someembodiments of the present disclosure.

FIG. 5A illustrates an exemplary transmission of electroniccommunication from an enterprise source to external recipients,according to some embodiments of the present disclosure.

FIG. 5B illustrates an exemplary transmission of electroniccommunication between sources and recipients within an enterprise,according to some embodiments of the present disclosure.

FIG. 6 illustrates an exemplary transmission of authenticablecommunication from an enterprise source 610 to external recipients,according to some embodiments of the present disclosure.

FIG. 7 illustrates exemplary authenticable communication exchanges,according to some embodiments of the present disclosure.

FIG. 8 illustrates an exemplary authenticable communication, wherein theauthenticable communication may comprise a video.

FIG. 9 illustrates an exemplary authenticable communication, wherein theauthenticable communication may comprise an article with an embeddedvideo.

FIG. 10 illustrates exemplary method steps for requesting a sourceauthentication, according to some embodiments of the present disclosure.

FIG. 11 illustrates exemplary method steps for transmitting anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 12 illustrates exemplary method steps for transmitting an internalenterprise communication, according to some embodiments of the presentdisclosure.

FIG. 13 illustrates exemplary method steps for transmitting an externalemail, according to some embodiments of the present disclosure.

FIG. 14 illustrates exemplary method steps for authenticating a sourceof an authenticable communication, according to some embodiments of thepresent disclosure.

FIG. 15 illustrates exemplary method steps for providing anauthenticable communication.

FIG. 16 illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 17A illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 17B illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 17C illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 18A illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 18B illustrates exemplary process steps for providing content in anauthenticable communication, according to some embodiments of thepresent disclosure.

FIG. 19A illustrates exemplary process steps for providing content in aninternal authenticable communication, according to some embodiments ofthe present disclosure.

FIG. 19B illustrates exemplary process steps for providing content in aninternal authenticable communication, according to some embodiments ofthe present disclosure.

FIG. 20A illustrates exemplary process steps providing content in apersonal authenticable communication, according to some embodiments ofthe present disclosure.

FIG. 20B illustrates exemplary process steps providing content in apersonal authenticable communication, according to some embodiments ofthe present disclosure.

FIG. 21A illustrates exemplary process steps for providing content foran authenticable communication through an external authenticationcommunication, according to some embodiments of the present disclosure.

FIG. 21B illustrates exemplary process steps for providing content foran authenticable communication through an external authenticationcommunication, according to some embodiments of the present disclosure.

FIG. 21C illustrates exemplary process steps for providing content foran authenticable communication through an external authenticationcommunication, according to some embodiments of the present disclosure.

FIG. 22 illustrates an exemplary processing and interface system,according to some embodiments of the present disclosure.

FIG. 23 illustrates an exemplary block diagram of an exemplaryembodiment of a mobile device, according to some embodiments of thepresent disclosure.

DETAILED DESCRIPTION

The present disclosure provides generally for system and method ofauthenticating a source of electronic communication. According to thepresent disclosure, authenticable communications may allow forauthentication of a source of the electronic communication, which maylimit potential damage caused by fraudulent communications. In someaspects, an authenticable communication may allow the recipient toconfirm that the indicated source is the actual source of theauthenticable communication. In some embodiments, the authentication maynot require an exchange of encrypted communications or an exchange ofcommunications solely within the same communication system.Authenticable communications may provide a separate layer of securitythat may allow a recipient to review the contents with confidence thatthe communication is not fraudulent. Further, authenticablecommunications may provide the additional security without requiringspecialized software.

In the following sections, detailed descriptions of examples and methodsof the disclosure will be given. The description of both preferred andalternative examples though thorough are exemplary only, and it isunderstood that to those skilled in the art variations, modifications,and alterations may be apparent. It is therefore to be understood thatthe examples do not limit the broadness of the aspects of the underlyingdisclosure as defined by the claims.

Glossary

Authenticable Communication: as used herein refers to an electroniccommunication with at least one source authentication mechanism. In someaspects, an electronic communication may comprise a direct communicationfrom a source to a recipient, such as an email, telemedicine,teleconferencing, video conferencing, or reservations. In someembodiments, an electronic communication may not have a specificrecipient, such as a video, social media post, ad, video games, orarticle. In some implementations, an authenticable communication may besent through an authenticable communication transmittal mechanism, suchas an email application, enterprise application, authentication module,or other communication system.

Authentication Screen: as used herein refers to a screen that may atleast partially obscure content in an authenticable communication,wherein the authentication screen may be removed when the authenticablecommunication is authenticated. In some embodiments, the authenticationscreen may be removed when one or both the sender or recipient isauthenticated. In some implementations, the content of an authenticablecommunication may comprise attachments, text, images, links, or fillableforms, as non-limiting examples. In some embodiments, an authenticationscreen may comprise a message that may provide authenticationinformation to a recipient, such as the purpose of the authenticationscreen, a prompt to authenticate, or an indication of the contents, asnon-limiting examples.

Source Authentication: as used herein refers to verifying or confirmingthe source of an electronic communication. In some aspects, the sourcemay be an individual person, such as a sender of an email or an authorof an article. In some embodiments, the source may be an entity, such asan enterprise, business, or group. In some implementations, sourceauthentication may occur by comparing an indicated source of anauthenticable communication with the actual source. In some embodiments,the authenticable communication may further allow for verification thatthe recipient was the intended recipient.

Indicated Source: as used herein refers to an apparent source of anauthenticable communication. For example, an indicated source maycomprise an email address of a sender. In some aspects, a source may beindicated through branding or labeling on or near the authenticablecommunication. For example, an indicated source may comprise a personassociated with a known social media handle, wherein the social mediahandle may be the apparent poster of a social media post. As anotherexample, an indicated source may comprise an entity associated with alogo, wherein the logo may be embedded in a video.

Actual Source: as used herein refers to the true source of anauthenticable communication. In some aspects, source authentication mayconfirm the indicated source and the actual source are the same. In someembodiments, source authentication may reject the indicated source andmay find that the actual source of the authenticable communication isnot the indicated source. In some non-limiting exemplary embodiments, anactual source may comprise a human, one or more machine learning orartificial intelligence algorithms, or both.

Referring now to FIG. 1 , an exemplary system of source authenticationof an authenticable communication 120 is illustrated. In some aspects, asource 110 may comprise a person or entity. In some embodiments, theauthenticable communication 120 may comprise an indicated source,recipient, subject, and text body. In some implementations, therecipient may want to authenticate the source of the authenticablecommunication 120, such as where the authenticable communication 120 mayinclude personal information, financial instruction, or other privatecommunication.

In some aspects, a recipient may request source authentication, such asby clicking an icon within the email application. In someimplementations, an authentication request may be transmitted to anindicated source 130. In some embodiments, a source authentication maycomprise sending a text message to a phone number associated with theindicated source 130. In some aspects, a profile may be associated witha source, which may allow for the transmission of authenticationrequests when the indicated source is associated with the profile.

In some implementations, the response to the authentication request maybe

transmitted to an authentication system 140. In some aspects, the resultof the authentication result may be transmitted back to the recipient.For example, a positive result may change an icon to a green check mark,and a negative result may change an icon to a red stop sign, which mayindicate that the indicated source is not the actual source, such asthrough spoofing.

Referring now to FIG. 2A, an exemplary authenticable communication 200with an icon authentication 210 and barcode authentication 220, isillustrated. Referring now to FIG. 2B, an exemplary authenticablecommunication 200 with a QR code authentication 240 and a numeric grid250, is illustrated. In some aspects, the authenticable communication200 may comprise a phone number that a recipient may call to confirmthat the indicated sender is the actual sender. As part of theauthentication, the phone number may connect the recipient to anauthentication system. The authentication system may be automated,personal, or combinations thereof. The authentication system may confirmat least a portion of the authentication, such as for the iconauthentication 210 or numeric grid 250.

In some embodiments, customer service may send an authenticablecommunication to a customer who is calling in as a substitute forrequesting for confidential information. For example, typically,customer service may request a portion of the customer's social securitynumber, and instead, by request or as part of a standard protocol,customer service may send the authenticable communication and requestthat the customer provide a portion of an identifier within theauthenticable communication. This may limit exchange of personal andconfidential information.

In some aspects, the authenticable communication 200 may comprise aphysical document, such as a letter sent through the mail. In someembodiments, an authenticable communication 200 may be scanned to read abarcode authentication 220. Depending on the indicated source, thescanning may occur through an enterprise software or through acentralized software that may process authenticable communications 200for multiple indicated sources. For example, the IRS or a large bank mayprovide an internal authentication module within their existingapplication or website. Hosting the programming within the enterprisemay increase the sense of security and confidence a recipient may havein the authentication. It may also keep the data internal withoutrequiring exchange of personal data or secure information throughexternal servers.

In some implementations, the authenticable communication 200 may besplit into multiple communications, which may comprise combinations ofdigital correspondence and paper correspondence. For example, arecipient may receive a physical letter with the icon identification 210prompting the recipient to log into their account for the contents oftheir authenticable communication 200, which may only be accessible oncethe recipient correctly inputs the requested icons from the iconidentification 210. Similarly, a recipient may receive a digital emailwith the icon identification 210 that may prompt the recipient to loginto a portal to retrieve the content of the authenticablecommunication. In some aspects where the authenticable communication 200may comprise multiple parts, the parts combined may be considered theauthenticable communication. In some embodiments where the authenticablecommunication 200 may comprise multiple parts, at least some of theseparate parts may be considered separate authenticable communications,including secondary authenticable communications.

In some embodiments, the authenticable communication 200 may comprise aproduct label that a recipient or potential purchaser may scan toauthenticate the indicated source as well as other productcharacteristics. For example, a recipient may want to verify whether aproduct is actually from the manufacturing company associated with abrand and not a knock off. As another example, a recipient may want toverify a quality of the product, such as a manufacturing origin,certifications, or general authenticity. In some aspects, actual sourcesmay provide an authentication module or participate in a collectiveauthentication module where recipients may authenticate authenticablecommunications 200.

Referring now to FIG. 3 , an exemplary graphical user interface (GUI)300 for an authentication system is illustrated. In some aspects, themethod of authentication 310 may be customizable, such as by a source,recipient, authentication application, or source enterprise, asnon-limiting examples. In some embodiments, the GUI 300 may allow asource to pre-select methods of authentication 310, which may includetext, image capture, email, phone call, handwriting recognition, facialrecognition, or voice recognition, as non-limiting examples.

Where the source may pre-select methods of authentication 310, thesource may also provide the base data for the methods of authentication310. For example, the source may provide the best phone number or emailaddress where the method of authentication 310 may comprise text oremail. As another example, the method of authentication 310 may comprisefacial recognition, and the GUI 300 may prompt facial capture to storethe authenticating facial data. As another example, where the methods ofauthentication 310 may comprise voice or handwriting recognition, theGUI 300 may prompt input of baseline data. For voice recognition, thesource may be prompted to speak a list of words or sounds, which mayallow for a randomized authentication. For handwriting recognition, thesource may be prompted to write a series of words or letters.

In some embodiments, the GUI 300 may be provided to a recipient orviewer, which may allow the recipient or viewer to select theirpreferred method of authentication 310. In some aspects, the selectionof the method of authentication 310 may be pre-set as a standard forauthenticable communications. In some implementations, the selection mayoccur for each authenticable communication. In some aspects, the methodsof authentication 310 may be ranked by preference, wherein theauthentication system may offer the method of authentication 310 withthe highest ranking if there are multiple methods of authentication 310offered with the authenticable communication.

As an illustrative example, a recipient may prefer text authentication,facial recognition authentication, then phone call authentication. Wherean authenticable communication may provide either phone callauthentication or text authentication, the authenticating system mayoffer the recipient only the text authentication. Where an authenticablecommunication may only offer handwriting authentication, the recipientmay still be given the option to request the authentication based onhandwriting authentication.

In some aspects, a recipient may decide to not authenticate anauthenticable communication. Were the recipient to declineauthentication, one or both the authenticable communication andauthentication system may contain or provide a disclaimer of liabilityrelated to the content within the authenticable communication. Where theauthentication system may be integrated as an add-on to a communicationsystem, the unauthenticated communication may be highlighted or flaggedas potentially fraudulent until or unless the recipient successfullyauthenticates the communication.

In some embodiments, a source may refuse to authenticate, or anauthentication may fail. In those cases, the recipient may receive afailure notification that warns against downloading, clicking, orperforming any requested action prompted by the authenticablecommunication. In some aspects, such as through an add-on feature to acommunication application, a failed authentication may cause acautionary step, such as automatically deleting, blurring, or disablingthe authenticable communication. In some implementations, such as wherethe authentication is controlled by an enterprise, a failure may furtherprompt reporting the failure to a regulating body, such as to an ITdepartment, compliance department, or to the authentication system, asnon-limiting examples. The reporting may flag one or more the type ofauthenticable communication, the authenticable communication, orindicated source of the authenticable communication as potentiallyfraudulent.

For example, an enterprise source may be an indicated source for a massdistribution authenticable communication. As authentications fail forthe authenticable communication, a reporting may allow the enterprise totake precautionary steps to limit any damage caused by the fraudulentcommunication. The enterprise may send out an alert to potentialrecipients to ignore and delete the fraudulent communication. Wherepractical, the enterprise may revoke the fraudulent communication.

As another example, an individual source may be an indicated source foran authenticable communication requesting a transfer of funds to aspecific account through an included link. A failed authentication mayalert the individual that their systems may have been corrupted, hacked,or compromised in some way. The individual may be able to store thefraudulent communication with their profile as a mechanism topotentially identify patterns of fraud. For example, if a secondauthentication fails with the same content, the authentication systemmay be able to identify a pattern, which may allow for a betterunderstanding of the fraudulent communication.

In some aspects, the authentication system may link or share fraud databetween users, which may allow for the anticipation of fraudulentcommunications. For example, the authentication system may identify anenterprise phishing scam email. One or both the language and the actualsource may be stored and flagged, wherein similar emails received fromdifferent enterprises or users may be more easily identified as fraud.In some embodiments, the authentication system may be accessed through asubscription model, such as by allowing a fixed number or type ofauthentication.

Referring now to FIG. 4 , exemplary authentication methods 410, 420,430, 440, 450 are illustrated. In some aspects, a method ofauthentication may depend on user settings, recipient communicationsettings, authenticable communication settings, source communicationsettings, authentication application. In some embodiments, theauthentication application may comprise a separate authenticationapplication or portal, a feature within an enterprise application, or anadd-on feature within the communication system.

In some implementations, authenticable communication may requiremultiple levels of authentication. In some aspects, one or more of: asource, recipient, or platform may set the number and types ofauthentication. In some embodiments, there may be a defaultauthentication method, such as a handwriting recognition 420, bar coderecognition 440, text authentication 410, or voice recognition, whereinthe authentication data may be stored with a source profile. In someimplementations, a recipient may request a separate type ofauthentication, which may or may not be verified or stored with thesource profile. For example, a recipient may request a facialrecognition snapshot 430, which may allow the recipient to confirm thesource independently. Randomized or custom authentication requests mayprovide a further layer of protection against fraud.

In some aspects, an authenticable communication may require amulti-layered authentication 450, such as requiring an icon selection,numeric matching, and voice recognition. A multi-layered authentication450 may provide increased security against fraud. For example, amulti-layered authentication 450 may be useful where the authenticablecommunication may be requesting a financial transaction, social securitynumber, or other action related to confidential information or finance.

Referring now to FIG. 5A, an exemplary transmission of electroniccommunication from an enterprise source 510 to external recipients isillustrated. Referring now to FIG. 5B, an exemplary transmission ofelectronic communication between sources and recipients within anenterprise 520. In some aspects, electronic communication from anenterprise source 510 may be sent to multiple recipients, wherein therecipients may want to know whether the communication is from theenterprise source 510 and not necessarily the person who may have sentit. In some embodiments, the source in communications within anenterprise 520 may be individuals, such as employees. In someimplementations, the source within an enterprise may comprisedepartments, such as from human resources or compliance.

In some embodiments, communications within an enterprise 520 may havehierarchies of authentication. For example, a low-level employee maynever send authenticable communication as their communications may nevercontain secure information, and each of their communications may bemarked as non-authenticable, which may provide sufficient warning to anyrecipients that their communications should not contain confidentialinformation. A manager may periodically send confidential informationand may designate authenticable communication based on the contents ofeach communication. Employees from the human resources department mayonly send authenticable communications because all or most of theircommunications may relate to confidential or personal data. Employeesfrom the finance department may only receive authenticablecommunications internally, which may limit the effectiveness offraudulent internal instructions.

In some aspects, the authentication may occur on the backend of thecommunication exchange, wherein the sources may not be required to takean additional step to authenticate a communication. In someimplementations, the authentication may occur through a third party,such as through a call center, an authentication system, or controllingdepartment, as non-limiting examples. For example, the IT department maybe responsible for authentications. In some embodiments, failedauthentications may prompt further action, such as investigation,blocking of the indicated source, or blocking of the actual source, asnon-limiting examples. Blocking the indicated source may be temporaryuntil the cause of the breach is further understood.

In some embodiments, the authentication may occur one way or two way.For one-way authentication, only the source may be authenticated, andfor two-way authentication, both the source and the recipient may beauthenticated. Two-way authentication may be useful to confirm thecorrect person received the authenticable communication. Further,two-way communication may allow for the open exchange of communicationswhere the recipient may reply to the authenticable communication andbecome the indicated source of the reply.

For example, a health care provider may transmit a document withinformation protected by HIPAA to a patient. It may be helpful orrequired to stay compliant to verify both the source and the recipient,which may occur automatically, manually, or a combination. A sourceauthentication may occur automatically once the authenticablecommunication is transmitted, and the recipient authentication may beinitiated by opening the authenticable communication. At least a portionof the contents of the authenticable communication, such as the personalor confidential material, may be obscured or blocked to the recipientuntil both the source and recipient are authenticated.

Referring now to FIG. 6 , an exemplary transmission of authenticablecommunication from an enterprise source 610 to external recipients 620is illustrated. In some aspects, some of the recipients may have anenterprise application on their portable device, such as a smartphone ortablet. Where the recipient may have the enterprise application, thetransmission of authenticable communication may be directly through theenterprise application. In some embodiments, some of the recipients mayonly receive authenticable communication through a secondarycommunication source, such as an email application. Where the recipientmay not have the enterprise application, the authenticable communicationmay be sent through a non-enterprise application.

In some aspects, such as where the authenticable communication may besent through an enterprise application, the authentication methods maybe less stringent than those sent through a third-party application. Forexample, source authentication for enterprise application authenticablecommunications may comprise a single authentication method that may beinternal to the enterprise application, and source authentication forexternal authenticable communications may comprise multipleauthentication methods that may require an affirmative authenticationrequest.

Referring now to FIG. 7 , exemplary authenticable communicationexchanges are illustrated. In some aspects, sources of authenticablecommunication may comprise employees within an enterprise 700. In someembodiments, a first employee 710 may exchange authenticablecommunications with a second employee 720. In some implementations, theindicated source may comprise an enterprise, wherein the authenticablecommunication may be external communications between external recipientsand one or more within the enterprise, 700 and the employees 710, 720.

In some aspects, employees may have a set of permissions and emailrequirements. Some may be required to use secure mail for both incomingand outgoing, such as an employee responsible for the exchange ofpersonal, private, confidential, or financial information. In someaspects, some mail types may be authenticable communication, such asthose containing personal, private, confidential, or financialinformation. In some embodiments, the source may identify the content ormail type, which may determine whether a communication is authenticableor not. In some implementations, the source may actively flag acommunication as authenticable, such as when the source wants to alertthe recipient that the contents need to be authenticated. Internalemails may automatically be checked, such as through the enterprisecommunication infrastructure.

Referring now to FIG. 8 , an exemplary authenticable communication 800is illustrated, wherein the authenticable communication 800 may begenerated from an electronic communication comprising original contentthat at least partially comprises one or more types of text or media,such as, for example and not limitation, at least one video, image,article, or sound recording, as non-limiting examples. In some aspects,the authenticable communication 800 may comprise at least oneauthentication mechanism that comprises at least one detectable element,such as, for example and not limitation, a logo; a watermark; aquick-response or “QR” code; a numeric grid; a grouping of one or moreletters, characters, words, or phrases; syntax; a grouping of one ormore pixels; an audio sound; an audio cue; a dialect; a tone; or anysimilar aspect associated with or that may be integrated with orembedded within one or more portions of an electronic communication,such as, for example and not limitation, the original content thereof

In some implementations, the authentication mechanism may be at leasttemporarily stored in at least one memory resource, such as, for exampleand not limitation, a database or hard drive. In some embodiments, theauthentication mechanism may comprise a correlation formed orestablished between the detectable element and a primary datatransmission pathway of a first electronic communication and/or theactual source of the first electronic communication such that uponsubsequent detection of the detectable element within a secondelectronic communication, a determination may be made whether the secondelectronic communication comprises the actual source and/or the primarydata transmission pathway, wherein a negative determination for one orboth of these aspects may indicate that the second electroniccommunication may comprise fraudulent, unauthorized, incomplete,misleading, or inaccurate content that comprises a replication of atleast a portion of the original content of the first electroniccommunication.

In some embodiments, an actual source of the authenticable communication800 may want to provide an authentication method for the authenticablecommunication 800 so that one or more of a plurality of potentialviewers or other recipients of the authenticable communication 800 mayhave confidence that the indicated source of the media or other contentof the authenticable communication 800 comprises the actual sourcethereof. In some implementations, this may detract from any legitimacythat may be associated with fake videos or other types of counterfeit orimitated media that may be incorrectly associated with an actual source.

In some aspects, the authentication method may at least partiallycomprise integrating or embedding one or more detectable elements in theform of identification icons or similar visual representations withwithin at least one portion of an authenticable communication 800, suchas, for example and not limitation, in the form of media, that may beassociated with the actual source of the authenticable communication 800such that the visual representation may be displayed with theauthenticable communication 800. In some implementations, the visualrepresentation may be correlated to the actual source of theauthenticable communication 800 or the primary data transmission pathwayof the authenticable communication 800 such that the presence of thevisual representation or other detectable element may be subsequentlydetected within an authenticable communication 800 to authenticate theauthenticable communication 800. By way of example and not limitation,one or more identification icons may be configured at a corner ofcontent of an authenticable communication 800 comprising a video at oneor more predetermined, preset, or expected time stamps. In somenon-limiting exemplary implementations, by correlating one or moreidentification icons with an actual source and/or a primary datatransmission pathway of an authenticable communication 800, theauthentication system or one or more users thereof may confirm or verifythat the content of the authenticable communication 800 was transmittedby or with the consent or authorization of the actual source.

In some non-limiting exemplary embodiments, the authenticablecommunication 800 may be at least partially generated and/or transmittedvia at least one authentication system. In some implementations, theauthentication system may provide an actual source of one or moreelectronic communications with the ability to register an electroniccommunication before transmitting it to one or more recipients, such as,for example and not limitation, one or more potential viewers of theelectronic communication. In some aspects, registration of theelectronic communication may at least partially comprise generating,embedding, integrating, or otherwise associating at least oneauthentication mechanism with the electronic communication to convertthe electronic communication to an authenticable communication 800. Insome embodiments, the electronic communication may be converted to anauthenticable communication 800 without first being registered. In someimplementations, the authentication system may provide a publicauthentication portal for the authenticable communication 800, which mayallow one or more viewers or other recipients of an electroniccommunication that comprises one or more detectable elements correlatingto one or more aspects of the authenticable communication 800 to submitat least one request to authenticate the electronic communication, suchas, for example and not limitation, using the authentication mechanismassociated therewith.

In some embodiments, the authentication mechanism of the authenticablecommunication 800 may be configured to confirm, verify, or authenticatea primary data transmission pathway of the authenticable communication800, wherein the primary data transmission pathway of the authenticablecommunication 800 may comprise original content transmitted from anactual source of the authenticable communication 800. In someimplementations, the primary data transmission pathway of theauthenticable communication 800 may comprise at least one datatransmission pathway associated with or used during a first or initialtransmission of the authenticable communication 800 from the actualsource to a one or more of a plurality of potential recipients, or uponthe registration of the authenticable communication 800 within at leastone authentication system. In some aspects, a potential recipient of theauthenticable communication 800 may comprise any user who may have thecapability and/or permission to access, view, or otherwise receive theauthenticable communication 800, while a recipient of the authenticablecommunication 800 may comprise any user who actually accesses, views, orotherwise receives the authenticable communication 800.

By way of example and not limitation, a primary data transmissionpathway of an authenticable communication 800 may comprise a media postor livestream on a social media site, a blog or article on a website orwebpage, or content generated and/or presented within a gaming orvirtual reality environment (such as, for example and not limitation,the metaverse), as non-limiting examples. In some aspects, the primarydata transmission pathway of the authenticable communication 800 may bereproduced such that the primary data transmission pathway may comprisean indefinite number of access or transmission occurrences, such as, forexample and not limitation, when a website or social media post may bevisited or viewed a plurality of times. In some implementations, theprimary data transmission pathway of the authenticable communication 800may comprise at least one repeatedly accessible data transmissionpathway from at least one storage medium, such as, for example and notlimitation, a webpage or social media post that may be downloaded aplurality of times from at least one server by one or more recipientsvia one or more client or local computing devices.

In some aspects, a transmission of an electronic communication that doesnot comprise the primary transmission may comprise a secondary datatransmission pathway. In some embodiments, an electronic communicationthat comprises a secondary data transmission pathway may originate fromat least one indicated source. In some implementations, such as, forexample and not limitation, when the same source posts a blog article ona website and a social media page, the indicated source of theelectronic communication comprising the secondary data transmissionpathway may be the same as the actual source of the authenticablecommunication 800 comprising the primary data transmission pathway. Insome aspects, the indicated source of one or more electroniccommunications comprising a secondary data transmission pathway may bedifferent from the actual source of the authenticable communication 800.

In some non-limiting exemplary embodiments, the authentication mechanismof an authenticable communication 800 comprising a detectable elementmay be configured to initiate or facilitate a determination of whether areceived transmission of an electronic communication comprising thedetectable element comprises a primary data transmission pathway or asecondary data transmission, wherein one or more results of suchdetermination may be presented to at least one recipient of theelectronic communication or to the actual source of the authenticablecommunication 800. By way of example and not limitation, suchdetermination may at least partially comprise determining whether thecurrent data transmission pathway of the electronic communication is thesame as the primary data transmission of the authenticable communication800, wherein the primary data transmission pathway of the authenticablecommunication 800 may be identified by the authentication mechanism,such as by referencing data stored in at least one memory resource, as anon-limiting example.

In some non-limiting exemplary implementations wherein theauthentication mechanism of an authenticable communication 800 mayfacilitate a determination that an electronic communication comprisingthe detectable element of the authenticable communication 800 comprisesa secondary data transmission pathway, the content of the electroniccommunication comprising the secondary data transmission pathway maycomprise replicated content, wherein one or more portions of thereplicated content of the electronic communication may be the same ordifferent as one or more portions of the original content of theauthenticable communication 800 comprising the primary data transmissionpathway.

In some embodiments, upon a determination that an electroniccommunication comprises a secondary data transmission pathway, theauthentication system associated with the authentication mechanism ofthe authenticable communication 800 may be configured to initiate orfacilitate at least one comparison between at least one portion of thereplicated content of the electronic communication with at least oneportion of the original content of the authenticable communication 800,wherein such comparison may enable the authentication system todetermine or identify one or more differences between the replicatedcontent and the original content, or to initiate or facilitate at leastone comparison between the indicated source of the electroniccommunication and the actual source of the authenticable communication800. In some aspects, the comparison may be automatically initiated bythe authentication system when the relevant transmission of the aelectronic communication is determined to comprise a secondary datatransmission pathway, or the comparison may be initiated via a requestreceived from at least one recipient of the electronic communication,the actual source of the authenticable communication 800, or any otheruser of the authentication system, regardless of whether thetransmission comprises a primary or secondary data transmission pathway.By way of example and not limitation, at least one difference betweenthe original content and the replicated content may comprise adifference in one or more of: a playback time duration, a presentationtime duration, at least one audio characteristic, or at least one visualcharacteristic, as non-limiting examples.

As a non-limiting illustrative example, in some aspects wherein theoriginal content of an authenticable communication 800 comprising aprimary data transmission pathway may comprise media in the form of alive or previously-recorded media playback that comprises audio andvideo components, the authentication system associated with theauthentication mechanism of the authenticable communication 800 maycompare the original video content with replicated video content as ofan electronic communication comprising a secondary data transmissionpathway to determine that the replicated content comprises a video thatis five seconds shorter than the original video content and comprisesaudio and visual characteristics that have been modified, enhanced, orgenerated by one or more artificial intelligence (“AI”) algorithms.

In some non-limiting exemplary implementations, the authenticationsystem associated with the authenticable communication 800 may beconfigured to compute, calculate, or otherwise determine at least onequantified representation of one or more results of a comparison betweenthe original content of the authenticable communication 800 and thereplicated content of an electronic communication. In some aspects, thequantified representation may comprise one or more of: a score, apercentage, a graph, a chart, or similar indicator of a degree ofsimilarity or difference between the original content and the replicatedcontent, wherein the quantified representation may be presented to atleast one user of the authentication system, such as, for example andnot limitation, via at least one graphical user interface displayed viaat least one display screen or monitor integrated with orcommunicatively coupled to at least one computing device. In someembodiments, the quantified representation may be presented to theactual source of the authenticable communication 800 or one or morerecipients of the electronic communication. In some aspects, theauthentication system may be configured to notify the actual source orthe recipient(s) of an electronic communication to be notified when anelectronic communication comprising one or more detectable elementsassociated with an authenticable communication 800 may comprisereplicated content that differs from the original content of theauthenticable communication 800 and/or whether the indicated source ofthe electronic communication differs from the actual source of theauthenticable communication 800.

As a non-limiting illustrative example, the authentication system may beable to determine that the replicated content of a secondarytransmission of an electronic communication comprising a secondary datatransmission pathway is 75% similar to the original content of therelevant authenticable communication 800, wherein the results of suchdetermination may be presented to at least one user of theauthentication system. In some non-limiting exemplary embodiments, theauthentication system may be configured to identify or determine one ormore differences between the original content and the replicated contentand present a list, summary, description, visual representation, orsimilar informative notification of such differences to one or moreusers of the authentication system.

In some implementations wherein a user of the authentication system mayview, access, or otherwise receive an electronic communicationcomprising a secondary data transmission pathway, the authenticationsystem may be configured to automatically notify or otherwise indicateto the user that the electronic communication comprises replicatedcontent that may be at least partially different from the originalcontent of the relevant authenticable communication 800 comprising oneor more detectable elements that may also be present in the electroniccommunication comprising the secondary data transmission pathway. Insome embodiments, the authentication system may initiate, eitherautomatically or at the request of the user, the simultaneouspresentation of the original content and the replicated content of theauthenticable communication 800 and the electronic communication,respectively, such as, for example and not limitation, in a side-by-sideformat for comparison, so that the user may inspect the original contentand the replicated to identify one or more differences therebetween. Insome aspects, the authentication system may be configured to indicate oridentify one or more aspects or characteristics of the replicatedcontent that may be different from the original content, such as, forexample and not limitation, by highlighting, bordering, or otherwiseemphasizing or drawing the user's attention to the suspicious,uncertain, or questionable portions of the replicated content. In someimplementations, the potentially different characteristics of thereplicated content may be emphasized without simultaneously presentingthe original content. In some aspects, a difference in the overallintent or meaning of the replicated content compared to the originalcontent may be identified or determined by the authentication system.

In some embodiments, the authentication system associated with anauthenticable communication 800 may be configured to notify the actualsource of the authenticable communication 800 any time the detectableelement(s) of the authentication mechanism are detected within anelectronic communication comprising a secondary data transmissionpathway. In some aspects, this may allow the actual source of theauthenticable communication 800 to monitor any electronic communicationsthat may comprise replicated content and stop, cease, discontinue, orotherwise terminate any unapproved or unauthorized reproduction(s) ofthe original content of the authenticable communication 800. In someembodiments, the authentication system may be configured to inform ordirect the actual source of the authenticable communication 800 of or tothe secondary transmission pathway comprising the electroniccommunication comprising replicated content so that the actual sourcemay view and assess the replicated content and become aware of where thereplicated content is posted or otherwise made available. In somenon-limiting exemplary implementations, any recipient or other user whoattempts to view, access, or otherwise receive an electroniccommunication comprising one or more detectable elements of anauthenticable communication 800 may be redirected, via a generated andprovided link or upon automatic initiation from the authenticationmechanism, to the authenticatable communication 800. In some aspects,this may increase the likelihood that the user views, accesses, orotherwise receives the original content of the authenticablecommunication 800 instead of replicated content, and may also enable theactual source of the authenticable communication 800 to be correctlyidentified.

As a non-limiting illustrative example, an authenticable communication800 may comprise a blog article, and the primary data transmissionpathway of the authenticable communication 800 may comprise a webpageassociated with the actual source of the article. In some aspects, anindicated source different from the actual source may repost the articlewithout permission on a social media site, wherein the social media siteposting may comprise an electronic communication comprising a secondarydata transmission pathway. In some implementations, the authenticationsystem of the authenticable communication 800 may be configured toautomatically redirect any recipient who receives the blog article on asocial media site to the webpage of the actual source of the articlewhile, in some embodiments, simultaneously or subsequently notifying theactual source of the unauthorized reposting of the article. In someaspects, this may allow the actual source of the blog article to becredited with providing or generating the article, as well as enable theactual source to take down or otherwise terminate the reposted blogarticle on the social media site. This may be useful, for example andnot limitation, when the electronic communication comprising thesecondary data transmission pathway may comprise replicated content thatdiffers at least partially from the original content of theauthenticable communication 800, which may cause confusion ormisunderstandings for recipients.

In some implementations, the authenticable communication 800 maycomprise at least one authentication mechanism in the form of at leastone verifiable token that may allow the authenticable communication 800to be authenticated any time it may be accessed, viewed, or otherwisereceived, whether via a primary or secondary data transmission pathway.In some non-limiting exemplary embodiments, the authentication mechanismmay be configured to be implemented or otherwise used independently ofan authenticable communication 800, wherein the authentication mechanismmay be configured to perform one or more authentication assessments onat least one portion of any electronic communication comprising anycontent from any source. By way of example and not limitation, theauthentication mechanism may be configured to determine if one or moreportions of the content of an electronic communication were at leastpartially generated by one or more AI or machine learning algorithms,such as, for example and not limitation, a natural language processingtool.

As a non-limiting illustrative example, an authentication mechanism maybe configured to be executed on content that at least partiallycomprises a video format. In some aspects, the authentication mechanismmay analyze one or more audio or visual characteristics of the video todetermine whether at least a portion of the video was at least partiallygenerated, edited, enhanced, augmented, or otherwise manipulated by oneor more AI, machine learning, or other computer algorithms such that thevideo may comprise a “deepfake” that may be misleading to one or morerecipients of the video.

In some implementations, an authentication system associated with anauthenticable communication 800 comprising one or more detectableelements may be configured to determine whether an indicated source ofan electronic communication comprising the detectable element(s) is thesame as the actual source of the authenticable communication 800. Insome non-limiting exemplary embodiments, the actual source of theauthenticable communication 800 may comprise one or more machinelearning, artificial intelligence, or similar computer algorithms. Insome aspects, original content produced or generated by computeralgorithms may comprise unique wording or syntax that may be indicativeof the computer algorithms, and such wording or syntax may comprise atleast a portion of the detectable elements of the authenticablecommunication. In some non-limiting exemplary implementations, theauthentication system may be configured to analyze the original contentproduced or generated by an actual source comprising one or morecomputer algorithms such that the authentication system may determineone or more inputs that likely facilitated generation of the content.

In some aspects, upon a determination of the inputs, the authenticationsystem may be configured to assess, analyze, or determine whether theoriginal content generated by the computer algorithms comprises contenttypically associated with such inputs, such as, for example and notlimitation, by referring to data in at least one database comprising oneor more correlations between one or more inputs and one or more types ofcorresponding content generated by computer algorithms.

In some aspects, an authenticable communication 800 may comprise a livefeed between at least one indicated source and at least one recipient,such as, for example and not limitation, for telemedicine, onlinegaming, teleconferencing, or distance education, as non-limitingexamples. Where the authenticable communication 800 may be live andongoing, authentication via at least one authentication mechanism mayoccur in substantially real time and/or may be periodic or otherwiserecurring to ensure that each indicated source continues to be an actualsource. By way of example and not limitation, an authentication systemmay periodically prompt a viewer or other recipient to input anauthenticating mark displayed on a portion of a video or may prompt anindicated source to be periodically authenticated as an actual source.As another non-limiting example, each participant of a conference callmay be considered an actual source, wherein each participate mayauthenticate their presence, such as through text, telephone number,email, or voice recognition, as non-limiting examples at one or moretunes during the call. In some aspects, participation in ateleconference call may be prohibited unless and until each actualsource is authenticated. Where the authentication may occur periodicallyduring the teleconference, a participant may be kicked out or otherwiseremoved from the teleconference if an authentication fails.

As a non-limiting illustrative example, a viewer or other recipient mayaccess an authentication portal via an authentication system website, anactual source website, or a third-party website, such as, for exampleand not limitation, the authenticable communication 800 platform. Insome aspects, the recipient may input at least one identifier for theauthenticable communication 800 via the authentication portal, such as,for example and not limitation, a title or label. In someimplementations, the portal may be configured to immediately determineand report that the authenticable communication 800 is not associatedwith the actual source thereof. In some embodiments, the portal mayfurther prompt the recipient to input an authentication mechanism, suchas one or more icons displayed at one or more predetermined time stampsassociated with content of the authenticable communication 800. In someaspects, the time stamp requests may be randomly generated, which mayfurther limit false positives.

In some implementations, the authentication portal may facilitatecollaboration between two or more users of the authentication system. Byway of example and not limitation, a user may use the authenticationportal to submit a request to an actual source of an authenticablecommunication 800 for authorization or approval to instigate or initiateat least one transmission of at least one electronic communicationcomprising replicated content that is at least partially similar to theoriginal content of the authenticable communication 800. As anon-limiting illustrative example, a user may use the authenticationportal to submit a request to an actual source of a blog on a website torepost the blog on the user's social media page or to initiate theformation of at least one licensing agreement, as non-limiting examples.

In some non-limiting exemplary implementations, two or more users mayuse the authentication portal to collaborate to generate content for aprimary transmission of an authenticable communication 800 such that aplurality of users may collectively comprise an actual source of theauthenticable communication 800, or the authenticable communication 800may comprise a plurality of actual sources. As a non-limitingillustrative example, a plurality of freelance journalists may use theauthentication portal to create a video and write an article about alocal sporting event, wherein the video and article may be presentedtogether as content for an online publication of a local newspaper.

Referring now to FIG. 9 , an exemplary authenticable communication 900is illustrated, wherein the authenticable communication 900 may comprisean article with an embedded video. In some aspects, one or both thearticle and the embedded video may each be associated with an indicatedsource, which may be the same or different. For example, and notlimitation, the video may be from a news source, and the article may beindependently written by an individual commenting on the material of thevideo but not associated with the news source.

As another non-limiting example, the embedded video may comprise anadvertisement that may be separate from the article. In some aspects,multiple authenticable communications 900 may be contained within thesame page, interface, or document. Where the authenticable communication900 may comprise a plurality of independent indicated sources, eachportion of the authenticable communication 900 associated with a uniqueindependent indicated source may be independently authenticated. By wayof example and not limitation, a viewer or other recipient of theauthenticable communication 900 may desire to authenticate the articleand may not care to authenticate the advertisement, as the viewer maynot be interested in interacting with the ad. As another non-limitingexample, an ad may appear to be associated with the article, so a viewermay want to authenticate only the embedded video to determine whether itis an advertisement or if it is pertinent to the article.

In some aspects wherein one or more of a plurality of indicated sourcesof an authenticable communication 900 may be different, each portion ofthe authenticable communication 900 may comprise separate sourceauthentications. In some implementations, each indicated source maycomprise a unique authentication process, such as through a phone call,authentication portal, or other authentication mechanism. In someembodiments, each indicated source may be authenticated through the sameauthentication system, which may allow for layered authentication.

As a non-limiting illustrative example, an article may comprise adual-layered authenticatable communication 900. In some aspects, aviewer may access the authentication method, input an authenticablecommunication identifier, such as a domain, title, or tag, and providetwo authentication requests. In some implementations, one request may bethrough the content of the article, and the other request may beacquired through navigating the embedded. In some embodiments, theindicated source of each portion of the authenticable communication 900may be separately authenticated, and the combination may also beauthenticated. Authenticating the combination may provide the viewerwith confidence that the authenticated article actually refers to theauthenticated video.

Referring now to FIG. 10 , exemplary method steps for requesting asource authentication are illustrated. At 1005, an authenticablecommunication may be received. In some aspects, at 1010, anauthentication method may be selected. In some embodiments, at 1015, anauthentication request may be transmitted. At 1020, the source may beauthenticated. At 1025, the authentication result may be received. Insome embodiments, at 1030, access to the authenticable communication maybe received. In some implementations, the steps from 1010 to 1020 may beautomated on a backend, wherein a recipient may not be required toperform additional actions to initiate the authentication. In someaspects, a recipient may initiate authentication, such as throughclicking an authenticate button within the communication system or byinputting authentication information into an authentication system.

In some embodiments, source authentication may be requested through asystem with system protocols. For example, the authenticablecommunication may comprise a document sent for secure signature from apredefined person, and the source authentication may occur automaticallywhen the executed document is received. The source authentication mayconfirm that the indicated source of the signer is the actual source andthat the actual source matches the predefined person. In some aspects,the source authentication for an executed document may be promptedmanually by a recipient trying to confirm that the predefined personactually executed the document. The source authentication may requestinput or scanning of a code or identifier on the document. The sourceauthentication may prompt a secondary authenticatable communication thatmay be generated to ensure the indicated source of the signature is theactual source.

In some aspects, authenticable communication may comprise a point ofaction communication, such as a purchase of a regulated product, voting,logging into a secure Wi-Fi system, transmission of personal health datato a health provider source, scanning a ticket for entrance into avenue, purchasing a ticket, boarding transportation, or other actionwhere confirming that the indicated source is the same as the actualsource is significant. In some embodiments, authentication may berequested automatically once the action is initiated. In some aspects,authentication may be requested prior to transmission of theauthenticable communication. For example, a vote in a political race maynot be officially transmitted until after the authentication occurs. Asanother example, sale of a lottery ticket may not be fully executed andtransmitted until the authentication further confirms the age of theactual source.

Referring now to FIG. 11 , exemplary method steps for transmitting anauthenticable communication are illustrated. In some embodiments, at1105, a communication may be designated as an authenticablecommunication. At 1110, an authenticable communication may betransmitted. In some implementations, at 1120, an authentication requestmay be received. At 1125, an authenticable communication may beauthenticated. In some aspects, at 1130, a notification of theauthentication result may be transmitted. In some embodiments, at 1135,access to the authenticable communication may be accessed. For example,wire information may be partially obscured until the source isauthenticated.

Referring now to FIG. 12 , exemplary method steps for transmitting aninternal enterprise communication are illustrated. At 1205, an internalcommunication may be transmitted. At 1210, the internal communicationmay be designated as authenticable communication. In some aspects, at1215, an authentication request may be received. At 1220, theauthenticable communication may be authenticated. In some embodiments,at 1225, an authentication result may be transmitted. In someimplementations, at 1230, access to the authenticable communication maybe allowed.

Referring now to FIG. 13 , exemplary method steps for transmitting anexternal email are illustrated. At 1305, an external enterprise emailmay be transmitted. In some aspects, at 1310, the enterprise email maybe designated as an authenticable communication. At 1315, anauthentication request option may be provided within the authenticablecommunication. In some embodiments, at 1320, an authentication requestmay be received. At 1325, the authenticable communication may beauthenticated. At 1330, the authentication results may be transmitted.

Referring now to FIG. 14 , exemplary method steps for authenticating asource of an authenticable communication is illustrated. At 1405, anauthentication request may be received. In some aspects, at 1410, anauthentication type may be received, such as where the authenticationtype may be selectable by one or both the recipient and the actualsource. At 1415, the authenticable communication may be accessed. At1420, the indicated source may be identified.

In some embodiments, at 1425, a secondary authentication request may betransmitted, such as to the indicated source, which may prompt an actionfrom the indicated source, and at 1430, the authentication response fromthe indicated source may be received. At 1435, the actual source may beidentified, which may be informed at least in part by the authenticationresponse received at 1430. At 1440, the indicated source may be comparedto the actual source.

In some implementations, at 1445, a recipient confirmation request maybe sent to the indicated source to confirm that the recipient orrecipients were the intended recipients of the authenticablecommunication. At 1450, the authentication results may be transmitted.In some aspects, the authentication results may be transmitted to theauthentication system, which may trigger access for the recipient to thecontents of the authenticable communication. In some embodiments, theauthentication may occur internally and automatically within the systemwithout notifications or prompts sent to the recipient or the indicatedsource. In some implementations, portions of the process may includenotifications or prompts to one or more of the indicated source, theactual source, and the recipient.

For example, where security may increase confidence in the authenticablecommunication, transmitting the authentication results at 1450 to therecipient may reassure the recipient that the authenticablecommunication is real and safe. As another example, such as withexchange of external authenticable communications, the enterprise may beconcerned with internal cybersecurity issues that may not affect or evenbe considered by the indicated source and the recipient. There, thesystem may perform the authentication internally without providingresults to the indicated source or the recipients.

Referring now to FIG. 15 , exemplary method steps for providing anauthenticable communication are illustrated. At 1505, an electroniccommunication may be received. In some aspects, at 1510, anauthentication type may be received, such as may be set or selected byan actual source, a recipient, or enterprise. At 1515, an authenticationmechanism may be integrated into the electronic communication. In someembodiments, at 1520, an authentication code may be generated for therecipient or recipients, wherein the authentication code may be uniqueto each recipient or general based on the indicated source. At 1525, theauthentication code into the electronic communication. At 1530, theelectronic communication may be converted to an authenticablecommunication, and at 1535, the authenticable communication may betransmitted to at least one recipient. In some implementations, theauthenticable communication may be presented to the actual source priorto the transmission at 1535.

Referring now to FIG. 16 , exemplary process steps for providing content1630 in an authenticable communication is illustrated. In some aspects,the institution 1600 may transmit a communication to an intendedrecipient 1610. In some embodiments, a communication may comprise anindicated source 1605, an intended recipient, and content 1630. In someimplementations, a communication may be converted to an authenticablecommunication 1615. In some aspects, a conversion may embed at least oneauthentication mechanism, such as described in FIGS. 2A-4 , asnon-limiting examples. In some embodiments, a conversion may embed anauthentication screen 1620, which may at least partially obscure content1630.

In some aspects, an authenticable communication 1615 may be transmittedto the intended recipient 1610. In some implementations, a recipient mayopen the authenticable communication 1615, such as by clicking into itthrough an email platform, and an authentication screen 1620 may atleast partially obscure content 1630. In some embodiments, theauthentication screen 1620 may cause or prompt authentication of one orboth the indicated source 1605 and the intended recipient 1610. Anauthentication screen 1620 may reappear based on predefined conditions,such as after a set amount of idle time or each time the authenticablecommunication 1615 is reopened, as non-limiting examples.

In some embodiments, the content 1630 may be provided in full to therecipient once the authentication screen 1620 is removed and one or boththe indicated source 1605 and the intended recipient 1610 areauthenticated. In some implementations, the authentication screen 1620may be used to ensure that the intended recipient 1610 opens content1630 safely. For example, content 1630 may comprise a link orattachments, and the intended recipient 1610 may click on the link orattachment, prompting the authentication screen 1620 to appear. In someimplementations, access to the attachments may be locked until one orboth the source and recipient are authenticated.

In some aspects, the locking may occur by withholding the attachmentsuntil authentication occurs. In some embodiments, the attachments may betemporarily stored in an intermediary database, such as anauthentication system. Once authenticated, the attachments may betransmitted and deleted from the intermediary storage, which may limitthe storage requirements and security risks for the authenticationsystem.

Requiring authentication of one or both the indicated source 1605 andthe intended recipient 1610 for the intended recipient 1610 to accesscontent 1630 may limit exposure to security risks or sharing ofsensitive information between incorrect parties. In some embodiments,the authentication screen 1620 may selectively obscure content 1630 thatmay be particularly sensitive or risky, such as links, attachments, andrequests for personal information. In some embodiments, the intendedrecipient 1610 may be provided a limited view of content 1630 that mayallow for general understanding of the purpose of the authenticablecommunication 1615 and may encourage authentication.

In some embodiments, an authenticable communication 1615 may comprise anarticle or news outlet, wherein a recipient 1610 may visit a website toaccess the authenticable communication 1615. In some aspects,authentication may allow the recipient to verify that the website waslegitimately from a known source. In some implementations,authentication may allow the recipient to verify the author of thearticle. This may allow for increased confidence in quality anddependability when reading articles.

Referring now to FIG. 17A-C, exemplary process steps for providingcontent in an authenticable communication 1715 is illustrated. In someaspects, an actual source 1700 may comprise an institution 1700 and maysend an intended recipient 1710 an authenticable communication 1715requesting information. In some aspects, the indicated source 1705 maydetermine which communications are sent with an authentication screen1720. In some embodiments, embedding an authentication screen 1720 maybe automatic based on predefined conditions, such as an externalcommunication, communications to specific recipients or recipientgroups, or content 1730, as non-limiting examples.

An authenticable communication 1715 may comprise an authenticationscreen 1720 that partially obscures content 1730 from the intendedrecipient 1710. In some aspects, the content 1730 may be completelyblocked. The level of content blocked may be set by an actual source1700, an intended recipient, a system, or combinations thereof. In someembodiments, a first authentication screen 1720 may authenticate theindicated source 1705 to confirm that it was an actual source 1700. Thismay provide the intended recipient 1710 with confidence knowing itoriginated from the indicated source 1705.

In some implementations, the content 1730 may request information fromthe recipient, and a recipient authentication screen 1740 may appear,which may request authentication of the intended recipient 1710. Forexample, before the user has full access to the content 1730, arecipient authentication screen 1740 may require specific informationfrom the recipient such as, but not limited to, a password, access code,or clearance level to access the content 1730. In some implementations,once an intended recipient is authenticated 1745, an information inputscreen 1750 may appear and prompt input of the requested informationfrom the content 1730. In some implementations, the recipient 1710 mayhave the ability to bypass the authentication screen 1720 based on theirclearance level, type of content 1730 and other non-limiting factors.

In some embodiments, the recipient authentication screen 1740 may looksimilar to that of the authentication screen. In some aspects, therecipient authentication screen 1740 may comprise an input mechanism andprompt for information known by one or both the authentication systemand the indicated source 1705. In some embodiments, the recipientauthentication screen 1740 may have a series of questions rather thanone singular question. In some embodiments, the intended recipient 1710may be granted access to the content 1730 once all questions or requiredinformation has been provided and verified.

In some aspects, the information input screen 1750 may auto trigger areply communication once the intended recipient 1710 has put in theirinformation, and the communication reply may populate the response withthe collected information 1755. In some aspects, the reply communicationmay be to a different address than the original sender. For example, thegeneral email address for an institution may be the actual sender, and areply communication may go to a specific individual within theinstitution assigned to the account. In some aspects, once theinformation input screen 1740 has been bypassed or completed, then thepopulated information 1745 may populate into the authenticablecommunication 1715.

In some implementations, the authenticable communication 1715 maycomprise a document, such as a Word document or Adobe PDF. Theauthentication may occur within the document, wherein content access andediting abilities may be locked to one or both a recipient or source isauthenticated. This may allow for secure access and editing ofdocuments, such as may be useful for tax documents, documents requiringsignature, or documents requesting sensitive information.

As an illustrative example, an authenticable communication 1715 mayrequest address, income, personal information of family members, and taxinformation, and an intended recipient may enter the information intothe information input screen 1750. That information may be populatedinto a response or directly into a system, such as through the actualsource. The authenticable communication 1715 may comprise internalfunctionality that may allow for direct collection of data from anintended recipient without requiring a reply or other additionalrecipient actions.

In some embodiments, the authentication process may continue within acommunication chain. For example, once the populated information 1755 issent back to the source 1700 or reply recipient, the source 1700 orreply recipient may be treated as a recipient, requiring authentication.When the source 1700 becomes the recipient, the method of authenticationmay be the same or different than the source authentication.

Referring now to FIG. 18A-B, exemplary process steps for providingcontent 1830 in an authenticable communication 1815 are illustrated. Insome aspects, the actual source 1800 may be an individual such as adoctor, tax person, lawyer, or professor as non-limiting examples. Insome aspects, the actual source 1800 may have a professionalrelationship with the intended recipient 1810 and may exchangeauthenticable communications 1815 when discussing sensitive topics, suchas health care, financial, or legal. In some aspects, the actual source1800 may send an authenticable communication 1815, and an authenticationscreen 1820 may pop up when the intended recipient 1810 attempts toaccess the content 1830.

The authentication screen 1820 may at least partially obscure content1830 from the intended recipient 1810. In some aspects, the intendedrecipient 1810 may be required to actively request authentication of theindicated source 1800. In some implementations, authentication mayautomatically occur when the intended recipient attempts to access thecontent 1830, and the authentication screen 1820 may indicate theresults of the authentication. In some embodiments, authentication ofthe indicated source may require input from the intended recipient 1810into the authentication screen 1820.

In some embodiments, once the authentication screen 1820 has beenremoved and the indicated source authenticated, a pre-authenticationscreen 1835 may indicate that more authentication may be required tofully access the content 1830. In some embodiments, a pre-authenticationscreen 1835 may not always be needed after the authentication screen1820. In some embodiments, a pre-authentication screen 1835 andauthentication screen 1820 may be redundant and only one may be requiredto gain access. In some embodiments, the authentication screen 1820 maybe a precursor to the pre-authentication screen 1835 letting theintended recipient 1810 know that authentication may be required in thefollowing steps.

In some implementations, a recipient authentication screen 1840 mayrequire the intended recipient 1810 to enter required information, whichmay allow the system to confirm that the intended recipient 1810 is theactual recipient. In some embodiments, the recipient authenticationscreen 1840 may request a username and password, a pin, or otherauthenticating code to gain access to the content 1830. In some aspects,the recipient authentication screen 1840 may be predictable, wherein theintended recipient 1810 may input the same information each time. Insome implementations, the recipient authentication screen 1840 mayappear randomized, wherein the prompts may be selected from a group ofpredefined questions each time a recipient authentication screen 1840 ispresented.

Referring now to FIG. 19A-B, exemplary process steps for providingcontent 1930 in an internal authenticable communication 1915 areillustrated. In some aspects, the actual source 1900 may be aninstitution, company, or individual from within an institution orcompany, as non-limiting examples. In some embodiments, the intendedrecipients 1910 may be one or more individuals within an institution1900. In some aspects, an internal authenticable communication 1915 mayallow for automatic authentication of an indicated source 1900. In someimplementations, an authenticable communication 1915 may provide apre-authentication screen 1935 that may indicate that authentication maybe required from the recipient 1910. In some aspects, the recipientauthentication screen 1940 may require the intended recipient 1910 toput in their username and password, such as may be provided by theinstitution. In some aspects, the recipient authentication screen maypartially obscure the content 1930 until the intended recipient 1910 isauthenticated.

In some aspects, an intended recipient 1910 may initiate theauthentication and click on the pre-authentication screen 1935, whichmay prompt display of the recipient authentication screen 1940. In someembodiments, the content 1930 may be partially filtered based on theintended recipient 1910 and the clearance level of the person viewingthe content 1930. For example, one intended recipient 1910 may have adifferent view of the content 1930 than another. One recipient may havefull access to the content 1930 whereas another may only have view ofthe first part of the content 1930. As another example, all recipientsmay have a limited view of the content 1930, and then some recipientsmay gain further access based on their input on the recipientauthentication screen 1940.

Referring now to FIG. 20A-B, exemplary process steps providing contentin a personal authenticable communication 2015 are illustrated. In someaspects, the actual source 2000 may be an individual sending a personalauthenticable communication 2015 to an intended recipient 2010 who maybe a friend or acquaintance. In some embodiments, the actual source 2000may be sending a personal message to an intended recipient 2010. In someimplementations, a recipient may attempt to access the content 2030, andan authentication screen 2020 may obscure at least a portion of thecontent 2030. In some aspects, the authentication screen 2020 mayauthenticate the indicated source 2000.

In some embodiments, the initial authentication screen 2020 toseparately authenticate an indicated source 2000 may not be required. Insome aspects, a pre-authentication screen 2035 may serve as an initialscreen that may block the content 2030 and notify a recipient thatauthentication may be necessary. In some implementations, apre-authentication screen 2035 may provide a brief summary or hint tothe actual content 2030.

In some embodiments, one or both the pre-authentication screen 2035 andthe recipient authentication screen 2040 may provide information thatmay allow the intended recipient 2010 to personally confirm that theindicated source is the actual source 2000. For example, thepre-authentication screen 2035 may describe a personal memory or insidejoke. In some aspects, the questions presented in the recipientauthentication screen 2040 may allow the intended recipient 2010 topersonally confirm the indicated source 2005. This may allow for securecommunication between friends and acquaintances, where they couldexchange communications knowing only the intended recipient would beable to access the content 2030.

In some embodiments, the question or required information asked by therecipient authentication screen 2040 may ask a personal question or forpersonal information that may be known by the actual source 2000. Forexample, the security question may ask where the intended recipient 2010ate lunch last week with the indicated source 2005, their favoritehorror film, favorite television show, or nickname, as non-limitingexamples. In some implementations, the acceptable input to the promptmay be set by the actual source 2000, such as through an authenticationsystem database, where authentication mechanisms and authentication datamay be collected and stored.

In some aspects, content 2030 may be provided once the recipient hasbeen authenticated. In some embodiments, response data may betransmitted back to the actual source 2000. In some implementations, theintended recipient may have the ability to view the content 2030 in fullonce they have passed the recipient authentication screen 2040. In someaspects, the recipient 2010 may only have access to part of the content2030 depending on the answers provided.

Referring now to FIG. 21A-C, exemplary process steps for providingcontent 2130 for an authenticable communication 2115 through an externalauthentication communication 2160 are illustrated. In some aspects,source authentication may occur automatically and a sourceauthentication screen 2120 may be displayed to confirm to the recipientthat authentication occurred. In some embodiments, an intended recipientmay be registered with an authentication system, directly or indirectlythrough an actual source, wherein a destination for an externalauthentication communication 2160 may be predefined.

In some aspects, a pre-authentication screen 2135 may indicate to therecipient that they need to access an external authenticationcommunication 2160, such as text, email, push notification from asoftware application, or internal software application message, asnon-limiting examples. In some aspects, an external authenticationcommunication 2160 may be automatically transmitted when a recipientattempts to access the content 2130, such as when they open theauthenticable communication 2115, click into a pre-authentication screen2135, or explicit request transmission through the pre-authenticationscreen 2135.

In some embodiments, the external authentication communication 2160 mayprovide a time-limited code, wherein a recipient must input the codeinto a recipient authentication screen 2140 within a predefined time toaccess the content 2130. In some aspects, the recipient may have beenpre-enrolled in the authentication system that allows them toauthenticate the message containing the content 2130 from an externalsource.

In some aspects, the external authentication communication 2160 may betransmitted through a smart device, mobile device, or computer, asnon-limiting examples. In some aspects, the external authenticationcommunication 2160 may be transmitted through an app associated with theactual source, such as a banking application or tax providerapplication. In some embodiments, the external authenticationcommunication 2160 may be transmitted through a central authenticationapp, which may be used by multiple sources. In some aspects, clickinginto the authenticable communication 2115 may automatically send anauthentication code to the external source allowing the recipient toaccess the content 2130. In some aspects, the source may send anauthentication code through text, email or in-app depending on therecipient preference. In some implementations, pre-registeringrecipients may allow for efficient authentication without requiringlayers of logging in to separate systems and applications.

In some embodiments, once the recipient logs in then they may gainaccess to the recipient authentication screen 2140. In some embodiments,the recipient may then enter their access code or required informationto bypass the recipient authentication screen 2140 and view content2130. In some embodiments, the recipient may enter an access code,password and username, personal information, or any other non-limitingexample that may grant the recipient access to the content 2130.

In some embodiments, once the recipient has been authenticated, they maygain access to an information input screen 2150. In some embodiments,the information input screen 2150 may allow for direct input ofrecipient information based on source requested data. In someimplementations, the content 2130 may be fully accessible once therecipient has been granted by the system. In some implementations, thepopulated information 2155 may be directly input into a response ordocument that would be sent back to the actual source or anotherdesignated location.

As an illustrative example, the actual source may comprise a tax advisorwho may have a small local company. The tax advisor may periodicallysend and request sensitive information and documents to clients, and thetax advisor may not be large enough to have their own softwareapplication. The tax advisor may request that their clients registerwith an authentication system, which may require input of limitedpersonal information, contact information, and answers to predefinedquestions, as non-limiting examples. That information may be used tocreate a dynamic authentication method for each client. Some of theclients may prefer answering specific questions in a recipientauthentication screen 2140, and others may prefer receiving an externalauthentication communication 2160 that contains no personal information.

The tax advisor may be able to adjust the authentication requirementsdepending on the content of the authenticable communication. A generalinformation communication may not need to be authenticable. Acommunication providing tax guidance or other information that arecipient may only trust if it came directly from the tax advisor may beembedded with a source authentication screen and source authenticationmechanism. A communication sending or requesting personal documents andinformation may require a dual layer of authentication. In some aspects,the dual layer may comprise two separate authentication screens that mayseparately authenticate the source and the recipient. In someembodiments, the dual layer may comprise transmission of an externalauthentication communication that could only transmit to the recipientif the indicated source was the actual source.

The tax advisor may request that a client complete a form or providespecific information. For efficiency and security, once fullyauthenticated, an authenticable communication may prompt input of therequested information, which may be directly inserted or populated intothe reply or the document. This may limit the need to visit an externalsite or app to complete the request and may allow the recipient tooperate within the authenticable communication.

Referring now to FIG. 22 , an exemplary processing and interface system2200 is illustrated. In some aspects, access devices 2215, 2210, 2205,such as a paired portable device 2215 or laptop computer 2210 may beable to communicate with an external server 2225 through acommunications network 2220. The external server 2225 may be in logicalcommunication with a database 2226, which may comprise data related toidentification information and associated profile information. In someembodiments, the server 2225 may be in logical communication with anadditional server 2230, which may comprise supplemental processingcapabilities.

In some aspects, the server 2225 and access devices 2205, 2210, 2215 maybe able to communicate with a cohost server 2240 through acommunications network 2220. The cohost server 2240 may be in logicalcommunication with an internal network 2245 comprising network accessdevices 2241, 2242, 2243 and a local area network 2244. For example, thecohost server 2240 may comprise a payment service, such as PayPal or asocial network, such as Facebook or a dating website.

Referring now to FIG. 23 , an exemplary block diagram of an exemplary

embodiment of a mobile device 2302 is illustrated. The mobile device2302 may comprise an optical capture device 2308, which may capture animage and convert it to machine-compatible data, and an optical path2306, typically a lens, an aperture, or an image conduit to convey theimage from the rendered document to the optical capture device 2308. Theoptical capture device 2308 may incorporate a Charge-Coupled Device(CCD), a Complementary Metal Oxide Semiconductor (CMOS) imaging device,or an optical sensor of another type.

In some embodiments, the mobile device 2302 may comprise a microphone2310, wherein the microphone 2310 and associated circuitry may convertthe sound of the environment, including spoken words, intomachine-compatible signals. Input facilities 2314 may exist in the formof buttons, scroll-wheels, or other tactile sensors such as touch-pads.In some embodiments, input facilities 2314 may include a touchscreendisplay. Visual feedback 2332 to the user may occur through a visualdisplay, touchscreen display, or indicator lights. Audible feedback 2334may be transmitted through a loudspeaker or other audio transducer.Tactile feedback may be provided through a vibration module 2336.

In some aspects, the mobile device 2302 may comprise a motion sensor2338, wherein the motion sensor 2338 and associated circuity may convertthe motion of the mobile device 2302 into machine-compatible signals.For example, the motion sensor 2338 may comprise an accelerometer, whichmay be used to sense measurable physical acceleration, orientation,vibration, and other movements. In some embodiments, the motion sensor2338 may comprise a gyroscope or other device to sense differentmotions.

In some implementations, the mobile device 2302 may comprise a locationsensor 2340, wherein the location sensor 2340 and associated circuitrymay be used to determine the location of the device. The location sensor2340 may detect Global Position System (GPS) radio signals fromsatellites or may also use assisted GPS where the mobile device may usea cellular network to decrease the time necessary to determine location.In some embodiments, the location sensor 2340 may use radio waves todetermine the distance from known radio sources such as cellular towersto determine the location of the mobile device 2302. In some embodimentsthese radio signals may be used in addition to and/or in conjunctionwith GPS.

In some aspects, the mobile device 2302 may comprise a logic module2326, which may place the components of the mobile device 2302 intoelectrical and logical communication. The electrical and logicalcommunication may allow the components to interact. Accordingly, in someembodiments, the received signals from the components may be processedinto different formats and/or interpretations to allow for the logicalcommunication. The logic module 2326 may be operable to read and writedata and program instructions stored in associated storage 2330, such asRAM, ROM, flash, or other suitable memory. In some aspects, the logicmodule 2326 may read a time signal from the clock unit 2328. In someembodiments, the mobile device 2302 may comprise an on-board powersupply 2342. In some embodiments, the mobile device 2302 may be poweredfrom a tethered connection to another device, such as a Universal SerialBus (USB) connection.

In some implementations, the mobile device 2302 may comprise a networkinterface 2316, which may allow the mobile device 2302 to communicateand/or receive data to a network and/or an associated computing device.The network interface 2316 may provide two-way data communication. Forexample, the network interface 2316 may operate according to an internetprotocol. As another example, the network interface 2316 may comprise alocal area network (LAN) card, which may allow a data communicationconnection to a compatible LAN. As another example, the networkinterface 2316 may comprise a cellular antenna and associated circuitry,which may allow the mobile device to communicate over standard wirelessdata communication networks. In some implementations, the networkinterface 2316 may comprise a Universal Serial Bus (USB) to supply poweror transmit data. In some embodiments, other wireless links known tothose skilled in the art may also be implemented.

CONCLUSION

A number of embodiments of the present disclosure have been described.While this specification contains many specific implementation details,this should not be construed as limitations on the scope of anydisclosures or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of the present disclosure.

Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination or in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented incombination in multiple embodiments separately or in any suitablesub-combination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous.

Moreover, the separation of various system components in the embodimentsdescribed above should not be understood as requiring such separation inall embodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous. Nevertheless, it will be understood thatvarious modifications may be made without departing from the spirit andscope of the claimed disclosure.

What is claimed is:
 1. A computer-implemented method for providing anauthenticable communication, the computer-implemented method comprising:receiving a first electronic communication comprising at least an actualsource and original content; converting the first electroniccommunication to an authenticable communication, wherein convertingcomprises: generating at least one authentication mechanism for theauthenticable communication, wherein the at least one authenticationmechanism at least partially comprises at least one correlation betweenat least one detectable element of the first electronic communicationand an initial transmission of the first electronic communication,wherein the initial transmission of the first electronic communicationcomprises a primary data transmission pathway; and storing the at leastone authentication mechanism in at least one memory resource.
 2. Thecomputer-implemented method of claim 1, further comprising: receiving asecond electronic communication; and detecting the at least onedetectable element within the second electronic communication.
 3. Thecomputer-implemented method of claim 2, wherein the primary datatransmission pathway facilitates transmission of the authenticablecommunication to one or more of a plurality of potential recipients. 4.The computer-implemented method of claim 3, wherein the secondelectronic communication comprises a secondary data transmissionpathway, wherein the second electronic communication comprisesreplicated content transmitted from an indicated source to the one ormore of a plurality of potential recipients via the secondary datatransmission pathway.
 5. The computer-implemented method of claim 3,wherein the primary data transmission pathway of the authenticablecommunication comprises a repeatedly accessible data transmissionpathway from at least one storage medium.
 6. The computer-implementedmethod of claim 5, wherein the primary data transmission pathway of theauthenticable communication is configured to be accessed a plurality oftimes from at least one server by the one or more of a plurality ofpotential recipients via one or more computing devices.
 7. Thecomputer-implemented method of claim 4, further comprising: comparing atleast one portion of the replicated content of the second electroniccommunication with at least one portion of the original content of theauthenticable communication.
 8. The computer-implemented method of claim7, wherein comparing the at least one portion of the replicated contentof the second electronic communication with the at least one portion ofthe original content of the authenticable communication identifies atleast one difference between the replicated content and the originalcontent.
 9. The computer-implemented method of claim 7, furthercomprising: determining at least one quantified representation of one ormore results of the comparison between the original content of theauthenticable communication and the replicated content of the secondelectronic communication.
 10. The computer-implemented method of claim9, wherein the at least one quantified representation comprises at leastone indicator of a degree of similarity between the original content andthe replicated content.
 11. A computer-implemented method for providingan authenticable communication, the computer-implemented methodcomprising: receiving a first electronic communication comprising atleast an actual source and original content; converting the firstelectronic communication to an authenticable communication, whereinconverting comprises: generating at least one authentication mechanismfor the authenticable communication, wherein the at least oneauthentication mechanism at least partially comprises at least onecorrelation between at least one detectable element of the firstelectronic communication and the actual source of the first electroniccommunication; and storing the at least one authentication mechanism inat least one memory resource.
 12. The computer-implemented method ofclaim 11 further comprising: receiving a second electroniccommunication; and detecting the at least one detectable element withinthe second electronic communication.
 13. The computer-implemented methodof claim 12, wherein the second electronic communication comprisesreplicated content from an indicated source.
 14. Thecomputer-implemented method of claim 13, further comprising: comparingthe indicated source to the actual source.
 15. The computer-implementedmethod of claim 14, further comprising: determining that the indicatedsource does not comprise the actual source; and comparing at least oneportion of the replicated content of the second electronic communicationwith at least one portion of the original content of the authenticablecommunication.
 16. The computer-implemented method of claim 15, whereincomparing the at least one portion of the replicated content of thesecond electronic communication with the at least one portion of theoriginal content of the authenticable communication identifies at leastone difference between the replicated content and the original content.17. The computer-implemented method of claim 15, further comprising:determining at least one quantified representation of one or moreresults of the comparison between the original content of theauthenticable communication and the replicated content of the secondelectronic communication.
 18. The computer-implemented method of claim17, wherein the at least one quantified representation comprises atleast one indicator of a degree of similarity between the originalcontent and the replicated content.
 19. The computer-implemented methodof claim 15, further comprising: transmitting at least one notificationto the actual source, wherein the at least one notification indicatesthe receipt of the second electronic communication.
 20. Thecomputer-implemented method of claim 15, further comprising:transmitting at least one notification to at least one recipient of thesecond electronic communication, wherein the at least one notificationindicates that the indicated source is not the actual source.